Correct some documentation in Data Fetching page #70394
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
xugetsu
commented
Sep 24, 2024
docs/02-app/01-building-your-application/02-data-fetching/01-fetching.mdx
Outdated
Show resolved
Hide resolved
docs/02-app/01-building-your-application/02-data-fetching/01-fetching.mdx
Outdated
Show resolved
Hide resolved
ijjk
approved these changes
Sep 24, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
This PR corrects and improves the documentation on the Data Fetching page, ensuring that the information is accurate and clear.
Why?
The previous version of the documentation contained inaccuracies or unclear explanations that could lead to confusion for developers. By addressing these issues, the documentation becomes more reliable and user-friendly.
How?
The changes involve updating the text to correct any misleading statements, adding clarity where necessary, and ensuring that all examples and explanations accurately reflect the intended data fetching process.